home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.cs.arizona.edu
/
ftp.cs.arizona.edu.tar
/
ftp.cs.arizona.edu
/
icon
/
newsgrp
/
group00b.txt
/
000079_icon-group-sender_Thu Oct 19 08:18:41 2000.msg
< prev
next >
Wrap
Internet Message Format
|
2001-01-03
|
1KB
Return-Path: <icon-group-sender>
Received: (from root@localhost)
by baskerville.CS.Arizona.EDU (8.11.1/8.11.1) id e9JFGGE01173
for icon-group-addresses; Thu, 19 Oct 2000 08:16:16 -0700 (MST)
Message-Id: <200010191516.e9JFGGE01173@baskerville.CS.Arizona.EDU>
Date: Wed, 18 Oct 2000 16:49:29 -0700 (PDT)
From: Shamim Mohamed <shamim@drones.com>
To: "Charles Hethcoat" <CHETHCOA@oss.oceaneering.com>
Cc: <icon-group@optima.CS.Arizona.EDU>
Subject: Re: Pipes in Icon
Errors-To: icon-group-errors@optima.CS.Arizona.EDU
Status: RO
Content-Length: 459
> This implies that each open() can open only a single, unidirectional
> pipe to a fresh instance of /usr/bin/xyz. And that is true. When I
> did this, I got two separate instances of xyz, each running a
> separate pipe.
True. If you want a bi-directional connection to a process, you need a
pair of pipes. This is easy to do in Unicon with filepair() - the
equivalent of the socketpair(2) system call - but I don't think it can
be done in Icon.
-s